Evolution of the Transfer Code of Practice

The Transfer Code of Practice was launched in 2008 as a set of best-practice guidelines to be followed when a journal changes publisher, with the aim of ensuring uninterrupted access to content for subscribers. The Code has now been updated to refl ect the continued evolution of the academic publishing process driven by new technologies, policies, and publishing practices. Introduction The process of transferring a journal between publishers is common and yet surprisingly complex. Data need to be transferred accurately and rapidly, systems have to be updated, access for subscribers must be maintained, and customers should be told exactly what is happening and when. Many publishers are well aware of the issues, and navigate these challenges seamlessly. But some are not, and things can go wrong – two of the reasons why, in 2006, a small group of publishers, librarians, and other publishing stakeholders formed the Transfer Working Group. Its aim was to provide some simple guidance for publishers, an initiative that is now known as the Transfer Code of Practice. With support from UKSG1 the Transfer Working Group released the fi rst iteration of the Code in 2008.2 Following a period of consultation, the Code was updated to Version 2 shortly afterwards, but has remained effectively unchanged since then. The Transfer Code is intended to be more than a set of guidelines. It is a way for publishers to show that, during the journal transfer process, they will adhere to the standards of quality and performance that the Code embodies. Publishers can publicly endorse the Code, and they are then expected to follow the recommendations within it. Instances of non-compliance can be reported to the Transfer Working Group, which provides support and guidance for publishers, librarians, and other relevant stakeholders in the publishing process.